Essential Reading For Operations Teams To Sample Tencent Cloud Singapore Server Fault Troubleshooting Checklists

This article provides the operations team with an actionable "Must-Read Tencent Cloud Singapore Server Fault Troubleshooting Checklist Example" for operations teams. For common faults in Singapore, we have organized and troubleshooting strategies step by step to help shorten recovery time.

1. Preliminary Information Collection and Fault Localization

When receiving a fault alarm, first collect the impact scope, start time, alarm indicators, and user feedback. Confirm whether the issue is single-host or regional, distinguish between application, network, or cloud platform issues, and decide the priority for subsequent troubleshooting.

2. Network connectivity and latency checks

Check the status of VPC subnets, routing tables, and elastic network cards, and use tools like ping and traceroute to detect packet loss and hopping counts. Focus on network latency and packet loss changes from the Singapore data center to the origin to determine whether it is a link issue.

3. DNS and domain name resolution troubleshooting

Confirm that the Singapore instance IP addressed by the domain name is correct, and verify that the local DNS resolution matches the authoritative DNS. Troubleshoot DNS cache, TTL settings, and load balancing domain health check results to prevent misleading traffic through parsing.

4. Cloud console and resource status check

In Tencent Cloud Console, verify instance status, availability zone, elastic public IP binding, load balancing health check, and automatic recovery policies. Check for exceptions caused by instance isolation, upgrades, or quota restrictions.

5. Operating System and Service Process Diagnostics

Login instances check CPU, memory, processes, and port usage, and watch for sudden growth or bot processes. Review critical service logs, failed services and dependencies to restart, and prioritize restoring network ports provided by business processes.

6. Troubleshooting storage and disk IO

Check the cloud drive mount status, file system read-only, disk usage, and IO wait time. For database or file services, confirm whether disk performance bottlenecks, snapshots, or expansion operations have interrupted the IO to avoid data corruption.

7. Security group, ACL and firewall rule verification

Verify whether inbound and outbound rules for security groups and network ACLs are misconfigured causing service inaccessibility. Check for host firewalls (iptables/ufw) and operating system-level restrictions to ensure necessary ports remain open.

8. Centralized analysis of monitoring data and logs

Based on the monitoring platform, trace changes in indicators before and after failures (CPU, memory, network, IO). Centrally collect system and application logs, combine the alarm timeline to identify root causes and formulate rollback or repair strategies.

9. Common Fault Scenarios and Response Examples

Common scenarios such as sudden load spikes, network jitter, disk exhaustion, and DNS resolution errors are listed, and immediate mitigation measures are provided: scaling instances, temporary route adjustments, disk cleanup, and rolling back DNS records to ensure service availability.

10. Review and protection recommendations after recovery

After fault recovery, SLA comparisons and reviews are conducted, recording root causes, handling processes, and improvement measures. It is recommended to improve monitoring thresholds, automated scripts, backup, and disaster recovery drills to reduce the likelihood of similar faults recurring in Singapore.

Conclusion and recommendations for action

This "Must-Read Tencent Cloud Singapore Server Troubleshooting Checklist Example" provides step-by-step troubleshooting and common solutions. It is recommended to incorporate the inventory into the operations manual and combine it with automation tools, regularly rehearsing and continuously optimizing monitoring strategies.